Compare Page

Semantic consistency

Characteristic Name: Semantic consistency
Dimension: Consistency
Description: Data is semantically consistent
Granularity: Element
Implementation Type: Rule-based approach
Characteristic Type: Declarative

Verification Metric:

The number of semantically inconsistent data reported per thousand records

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines: Scenario:
Ensure that semantics of data is consistent within/across applications (1) All orders placed by the customers are called “Sales order” in all tables/databases.
(2) Anti-example:
Payment type ( Check)
Payment Details (Card type,
Card number)
Maintenance of data dictionary or standard vocabularies of data semantics (1) Data dictionary provides technical data as well as semantics of data

Validation Metric:

How mature is the creation and implementation of the DQ rules to maintain semantic consistency

These are examples of how the characteristic might occur in a database.

Example: Source:
School admin: a student’s date of birth has the same value and format in the school register as that stored within the Student database. N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013.
A company has a color field that only records red, blue, and yellow. A new requirement makes them decide to break each of these colors down to multiple shadings and thus institute a scheme of recording up to 30 different colors, all of which are variations of red, blue, and yellow. None of the old records are updated to the new scheme, as only new records use it. This data- base will have inconsistency of representation of color that crosses a point in time. J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition: Source:
Data about an object or event in one data store is semantically Equivalent to data about the same object or event in another data store. ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing.
Data is consistent if it doesn’t convey heterogeneity, neither in contents nor in form – anti examples: Order.Payment. Type = ‘Check’; Order. Payment. CreditCard_Nr = 4252… (inconsistency in contents); Order.requested_by: ‘European Central Bank’;Order.delivered_to: ‘ECB’ (inconsistency in form,because in the first case the customer is identified by the full name, while in the second case the customer’s acronym is used). KIMBALL, R. & CASERTA, J. 2004. The data warehouse ETL toolkit: practical techniques for extracting. Cleaning, Conforming, and Delivering, Digitized Format, originally published.
The extent of consistency in using the same values (vocabulary control) and elements to convey the same concepts and meanings in an information object. This also includes the extent of semantic consistency among the same or different components of the object. STVILIA, B., GASSER, L., TWIDALE, M. B. & SMITH, L. C. 2007. A framework for information quality assessment. Journal of the American Society for Information Science and Technology, 58, 1720-1733.

 

Data volume

Characteristic Name: Data volume
Dimension: Completeness
Description: The volume of data is neither deficient nor overwhelming to perform an intended task
Granularity: Information object
Implementation Type: Process-based approach
Characteristic Type: Usage

Verification Metric:

The number of tasks failed or under performed due to not meeting the right volume of data
The number of complaints received due to volume related issues

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines: Scenario:
Define the scope of data in terms of organisational coverage to perform a business activity (1) At least 70% of the production units should submit data to calculate total production efficiency of the company
Define the scope of data in terms of activities relates to any business task (1) Pages with more than thousand
hits per day and above are considered for the analysis
Define the scope of data in terms of the population of data which is under concern (1) At least 10% of the population of white blood cells in the culture should be collected as samples to calculate its growth
Define an appropriate amount of records in terms of lower limit and upper limit for any task (1) At least six responses should be available to evaluate a tutor's skills and competency.

Validation Metric:

How mature is the process of defining and maintaining appropriate data volumes of data

These are examples of how the characteristic might occur in a database.

Example: Source:
At the end of the first week of the Autumn term, data analysis was performed on the ‘First Emergency Contact Telephone Number’ data item in the Contact table. There are 300 students in the school and 294 out of a potential 300 records were populated, therefore 294/300 x 100 = 98% completeness has been achieved for this data item in the Contact table. N. Askham, et al., “The Six Primary Dimensions for Data Quality Assessment: Defining Data Quality Dimensions”, DAMA UK Working Group, 2013.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition: Source:
A measure of the availability and comprehensiveness of data compared to the total data universe or population of interest. D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008.
Is the scope of information adequate? (not too much nor too little). EPPLER, M. J. 2006. Managing information quality: increasing the value of information in knowledge-intensive products and processes, Springer.
Degree of presence of data in a given collection. SCANNAPIECO, M. & CATARCI, T. 2002. Data quality under a computer science perspective. Archivi & Computer, 2, 1-15.
The quantity or volume of available data is appropriate WANG, R. Y. & STRONG, D. M. 1996. Beyond accuracy: What data quality means to data consumers. Journal of management information systems, 5-33.